Coded vision system

ABSTRACT

A system and method for presentation of computer vision (e.g., augmented reality, virtual reality) using user data and a user code is disclosed. A client device can detect an image feature (e.g., scannable code) in one or more images. The image feature is determined to be linked to a user account. User data from the user account can then be used to generate one or more augmented reality display elements that can be anchored to the image feature in the one or more images.

RELATED APPLICATIONS

This application is a continuation of and claims the priority benefit ofU.S. patent application Ser. No. 15/667,345, filed Aug. 2, 2017, whichclaims the priority benefit of U.S. Provisional Application No.62/446,753, filed on Jan. 16, 2017, which is hereby incorporated byreference in its entirety.

TECHNICAL FIELD

Embodiments of the present disclosure relate generally to virtualdisplay and, more particularly, but not by way of limitation, tocomputer vision using coded user data.

BACKGROUND

Client devices, such as smartphones, have image sensors that enableusers to view their environments through displays of the client devices.However, users cannot currently use their social media content tointeract with each other through the displays.

BRIEF DESCRIPTION OF THE DRAWINGS

To easily identify the discussion of any particular element or act, themost significant digit or digits in a reference number refer to thefigure (“FIG.”) number in which that element or act is first introduced.

FIG. 1 is a block diagram showing an example messaging system forexchanging data (e.g., messages and associated content) over a network.

FIG. 2 is block diagram illustrating further details regarding amessaging system having an integrated virtual object machine learningsystem, according to example embodiments.

FIG. 3 is a schematic diagram illustrating data which may be stored in adatabase of a messaging server system, according to certain exampleembodiments.

FIG. 4 is a schematic diagram illustrating a structure of a message,according to some embodiments, generated by a messaging clientapplication for communication.

FIG. 5 is a schematic diagram illustrating an example access-limitingprocess, in terms of which access to content (e.g., an ephemeral messageand associated multimedia payload of data) or a content collection(e.g., an ephemeral message story) may be time-limited (e.g., madeephemeral).

FIG. 6 shows internal functional components of a coded vision system,according to some example embodiments.

FIG. 7 shows a flow diagram for a method of implementing computer visionusing coded user data, according to some example embodiments.

FIGS. 8A and 8B show example user interfaces of computer vision usingcoded user data, according to some example embodiments.

FIG. 9 shows a flow diagram for a method for implementing augmentedreality using user data and a coded image feature, according to someexample embodiments.

FIGS. 10A-C show an example client device implementing augmented realityusing user data and coded image features, according to some exampleembodiments.

FIG. 11 shows a method for implementing augmented reality using userdata and coded image features, according to some example embodiments.

FIG. 12 is a block diagram illustrating a representative softwarearchitecture, which may be used in conjunction with various hardwarearchitectures herein described.

FIG. 13 is a block diagram illustrating components of a machine,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.

DETAILED DESCRIPTION

The description that follows includes systems, methods, techniques,instruction sequences, and computing machine program products thatembody illustrative embodiments of the disclosure. In the followingdescription, for the purposes of explanation, numerous specific detailsare set forth in order to provide an understanding of variousembodiments of the inventive subject matter. It will be evident,however, to those skilled in the art, that embodiments of the inventivesubject matter may be practiced without these specific details. Ingeneral, well-known instruction instances, protocols, structures, andtechniques are not necessarily shown in detail.

According to some example embodiments, a first user can display anobject using an image sensor of a client device (e.g., smartphone). Theobject is recognized as a scannable code linked to a second user'ssocial media account or avatar user account (e.g., Bitmoji® account). Afirst avatar for the first user is then arranged to appear interactingwith a second avatar of the second user. The arrangement of the twointeracting avatars may be preconfigured based on characteristics of thefirst avatar, the second avatar, or their relationship on a social mediaplatform. In some example embodiments, when the object is recognized aslinked to a given user's account, social media content (e.g., userimages) is integrated into a image display as augmented realityelements. For example, a user can scan a code of another user, and thelive video feed displayed on the user's phone can appear to have bubblesemanating from the code in the live video feed. The avatars or otheraugmented reality elements can be positionally anchored to the code inthe live video feed. Further actions may be triggered by scanning thecode, such as prompting a popup menu to add the user that corresponds tothe scanned code or install an app linked on the server side to acompany associated with the scanned code.

FIG. 1 is a block diagram showing an example messaging system 100 forexchanging data (e.g., messages and associated content) over a network.The messaging system 100 includes multiple client devices 102, each ofwhich hosts a number of applications including a messaging clientapplication 104. Each messaging client application 104 iscommunicatively coupled to other instances of the messaging clientapplication 104 and a messaging server system 108 via a network 106(e.g., the Internet).

Accordingly, each messaging client application 104 is able tocommunicate and exchange data with another messaging client application104 and with the messaging server system 108 via the network 106. Thedata exchanged between messaging client applications 104, and between amessaging client application 104 and the messaging server system 108,includes functions (e.g., commands to invoke functions) as well aspayload data (e.g., text, audio, video, or other multimedia data).

The messaging server system 108 provides server-side functionality viathe network 106 to a particular messaging client application 104. Whilecertain functions of the messaging system 100 are described herein asbeing performed by either a messaging client application 104 or by themessaging server system 108, it will be appreciated that the location ofcertain functionality within either the messaging client application 104or the messaging server system 108 is a design choice. For example, itmay be technically preferable to initially deploy certain technology andfunctionality within the messaging server system 108, but to latermigrate this technology and functionality to the messaging clientapplication 104 where a client device 102 has a sufficient processingcapacity.

The messaging server system 108 supports various services and operationsthat are provided to the messaging client application 104. Suchoperations include transmitting data to, receiving data from, andprocessing data generated by the messaging client application 104. Thisdata may include message content, client device information, geolocationinformation, media annotation and overlays, message content persistenceconditions, social network information, and live event information, asexamples. Data exchanges within the messaging system 100 are invoked andcontrolled through functions available via user interfaces (UIs) of themessaging client application 104.

Turning now specifically to the messaging server system 108, anApplication Programming Interface (API) server 110 is coupled to, andprovides a programmatic interface to, an application server 112. Theapplication server 112 is communicatively coupled to a database server118, which facilitates access to a database 120 in which is stored dataassociated with messages processed by the application server 112.

The API server 110 receives and transmits message data (e.g., commandsand message payloads) between the client devices 102 and the applicationserver 112. Specifically, the API server 110 provides a set ofinterfaces (e.g., routines and protocols) that can be called or queriedby the messaging client application 104 in order to invoke functionalityof the application server 112. The API server 110 exposes variousfunctions supported by the application server 112, including accountregistration; login functionality; the sending of messages, via theapplication server 112, from a particular messaging client application104 to another messaging client application 104; the sending of mediafiles (e.g., images or video) from a messaging client application 104 toa messaging server application 114 for possible access by anothermessaging client application 104; the setting of a collection of mediadata (e.g., a story); the retrieval of such collections; the retrievalof a list of friends of a user of a client device 102; the retrieval ofmessages and content; the adding and deletion of friends to and from asocial graph; the location of friends within the social graph; andopening application events (e.g., relating to the messaging clientapplication 104).

The application server 112 hosts a number of applications andsubsystems, including the messaging server application 114, an imageprocessing system 116, and a social network system 122. The messagingserver application 114 implements a number of message-processingtechnologies and functions, particularly related to the aggregation andother processing of content (e.g., textual and multimedia content)included in messages received from multiple instances of the messagingclient application 104. As will be described in further detail, the textand media content from multiple sources may be aggregated intocollections of content (e.g., called stories or galleries). Thesecollections are then made available, by the messaging server application114, to the messaging client application 104. Other processor- andmemory-intensive processing of data may also be performed server-side bythe messaging server application 114, in view of the hardwarerequirements for such processing.

The application server 112 also includes the image processing system116, which is dedicated to performing various image processingoperations, typically with respect to images or video received withinthe payload of a message at the messaging server application 114.

The social network system 122 supports various social networkingfunctions and services and makes these functions and services availableto the messaging server application 114. To this end, the social networksystem 122 maintains and accesses an entity graph (e.g., entity graph304 in FIG. 3) within the database 120. Examples of functions andservices supported by the social network system 122 include theidentification of other users of the messaging system 100 with whom aparticular user has relationships or whom the particular user is“following,” and also the identification of other entities and interestsof a particular user.

The application server 112 is communicatively coupled to a databaseserver 118, which facilitates access to a database 120 in which isstored data associated with messages processed by the messaging serverapplication 114.

FIG. 2 is block diagram illustrating further details regarding themessaging system 100, according to example embodiments. Specifically,the messaging system 100 is shown to comprise the messaging clientapplication 104 and the application server 112, which in turn embody anumber of subsystems, namely an ephemeral timer system 202, a collectionmanagement system 204, an annotation system 206, and a coded visionsystem 250.

The ephemeral timer system 202 is responsible for enforcing thetemporary access to content permitted by the messaging clientapplication 104 and the messaging server application 114. To this end,the ephemeral timer system 202 incorporates a number of timers that,based on duration and display parameters associated with a message orcollection of messages (e.g., a SNAPCHAT Story), selectively display andenable access to messages and associated content via the messagingclient application 104. Further details regarding the operation of theephemeral timer system 202 are provided below.

The collection management system 204 is responsible for managingcollections of media (e.g., collections of text, image, video, and audiodata). In some examples, a collection of content (e.g., messages,including images, video, text, and audio) may be organized into an“event gallery” or an “event story.” Such a collection may be madeavailable for a specified time period, such as the duration of an eventto which the content relates. For example, content relating to a musicconcert may be made available as a “story” for the duration of thatmusic concert. The collection management system 204 may also beresponsible for publishing an icon that provides notification of theexistence of a particular collection to the user interface of themessaging client application 104.

The collection management system 204 furthermore includes a curationinterface 208 that allows a collection manager to manage and curate aparticular collection of content. For example, the curation interface208 enables an event organizer to curate a collection of contentrelating to a specific event (e.g., delete inappropriate content orredundant messages). Additionally, the collection management system 204employs machine vision (or image recognition technology) and contentrules to automatically curate a content collection. In certainembodiments, compensation may be paid to a user for inclusion ofuser-generated content into a collection. In such cases, the curationinterface 208 operates to automatically make payments to such users forthe use of their content.

The annotation system 206 provides various functions that enable a userto annotate or otherwise modify or edit media content associated with amessage. For example, the annotation system 206 provides functionsrelated to the generation and publishing of media overlays for messagesprocessed by the messaging system 100. The annotation system 206operatively supplies a media overlay (e.g., a SNAPCHAT Geofilter orfilter) to the messaging client application 104 based on a geolocationof the client device 102. In another example, the annotation system 206operatively supplies a media overlay to the messaging client application104 based on other information, such as social network information ofthe user of the client device 102. A media overlay may include audio andvisual content and visual effects. Examples of audio and visual contentinclude pictures, texts, logos, animations, and sound effects. Anexample of a visual effect includes color overlaying. The audio andvisual content or the visual effects can be applied to a media contentitem (e.g., a photo) at the client device 102. For example, the mediaoverlay includes text that can be overlaid on top of a photographgenerated by the client device 102. In another example, the mediaoverlay includes an identification of a location (e.g., Venice Beach), aname of a live event, or a name of a merchant (e.g., Beach CoffeeHouse). In another example, the annotation system 206 uses thegeolocation of the client device 102 to identify a media overlay thatincludes the name of a merchant at the geolocation of the client device102. The media overlay may include other indicia associated with themerchant. The media overlays may be stored in the database 120 andaccessed through the database server 118.

In one example embodiment, the annotation system 206 provides auser-based publication platform that enables users to select ageolocation on a map and upload content associated with the selectedgeolocation. The user may also specify circumstances under whichparticular content should be offered to other users. The annotationsystem 206 generates a media overlay that includes the uploaded contentand associates the uploaded content with the selected geolocation.

In another example embodiment, the annotation system 206 provides amerchant-based publication platform that enables merchants to select aparticular media overlay associated with a geolocation via a biddingprocess. For example, the annotation system 206 associates the mediaoverlay of a highest-bidding merchant with a corresponding geolocationfor a predefined amount of time.

The coded vision system 250 manages tracking an object in differentimages, according to some example embodiments. Further details of thecoded vision system 250 are discussed below with reference to FIGS.6-11. Although the coded vision system 250 is illustrated in FIG. 2 asbeing integrated into the messaging client application 104, it isappreciated that in some example embodiments, the coded vision system250 is integrated into other systems, such as the application server112. Further, in some example embodiments, some engines of the codedvision system 250 may be integrated into the application server 112(e.g., to provide server side support to client generated requests) andsome may be integrated into the client device 102 (e.g., to generaterequests).

FIG. 3 is a schematic diagram illustrating data 300 which may be storedin the database 120 of the messaging server system 108, according tocertain example embodiments. While the content of the database 120 isshown to comprise a number of tables, it will be appreciated that thedata could be stored in other types of data structures (e.g., as anobject-oriented database).

The database 120 includes message data stored within a message table314. An entity table 302 stores entity data, including an entity graph304. Entities for which records are maintained within the entity table302 may include individuals, corporate entities, organizations, objects,places, events, and so forth. Regardless of type, any entity regardingwhich the messaging server system 108 stores data may be a recognizedentity. Each entity is provided with a unique identifier, as well as anentity type identifier (not shown).

The entity graph 304 furthermore stores information regardingrelationships and associations between or among entities. Suchrelationships may be social, professional (e.g., work at a commoncorporation or organization), interested-based, or activity-based,merely for example.

The database 120 also stores annotation data, in the example form offilters, in an annotation table 312. Filters for which data is storedwithin the annotation table 312 are associated with and applied tovideos (for which data is stored in a video table 310) and/or images(for which data is stored in an image table 308). Filters, in oneexample, are overlays that are displayed as overlaid on an image orvideo during presentation to a recipient user. Filters may be of varioustypes, including user-selected filters from a gallery of filterspresented to a sending user by the messaging client application 104 whenthe sending user is composing a message. Other types of filters includegeolocation filters (also known as geo-filters) which may be presentedto a sending user based on geographic location. For example, geolocationfilters specific to a neighborhood or special location may be presentedwithin a user interface by the messaging client application 104, basedon geolocation information determined by a Global Positioning System(GPS) unit of the client device 102. Another type of filter is a datafilter, which may be selectively presented to a sending user by themessaging client application 104, based on other inputs or informationgathered by the client device 102 during the message creation process.Examples of data filters include a current temperature at a specificlocation, a current speed at which a sending user is traveling, abattery life for a client device 102, or the current time.

Other annotation data that may be stored within the image table 308 isso-called “lens” data. A “lens” may be a real-time special effect andsound that may be added to an image or a video. In some exampleembodiments, the lens is stored as lens metadata which is retrievable ascontent 1135, discussed in further detail below.

As mentioned above, the video table 310 stores video data which, in oneembodiment, is associated with messages for which records are maintainedwithin the message table 314. Similarly, the image table 308 storesimage data associated with messages for which message data is stored inthe message table 314. The entity table 302 may associate variousannotations from the annotation table 312 with various images and videosstored in the image table 308 and the video table 310.

A story table 306 stores data regarding collections of messages andassociated image, video, or audio data, which are compiled into acollection (e.g., a SNAPCHAT Story or a gallery). The creation of aparticular collection may be initiated by a particular user (e.g., eachuser for whom a record is maintained in the entity table 302). A usermay create a “personal story” in the form of a collection of contentthat has been created and sent/broadcast by that user. To this end, theuser interface of the messaging client application 104 may include anicon that is user-selectable to enable a sending user to add specificcontent to his or her personal story.

A collection may also constitute a “live story,” which is a collectionof content from multiple users that is created manually, automatically,or using a combination of manual and automatic techniques. For example,a “live story” may constitute a curated stream of user-submitted contentfrom various locations and events. Users whose client devices havelocation services enabled and are at a common location or event at aparticular time may, for example, be presented with an option, via auser interface of the messaging client application 104, to contributecontent to a particular live story. The live story may be identified tothe user by the messaging client application 104, based on his or herlocation. The end result is a “live story” told from a communityperspective.

A further type of content collection is known as a “location story,”which enables a user whose client device 102 is located within aspecific geographic location (e.g., on a college or university campus)to contribute to a particular collection. In some embodiments, acontribution to a location story may require a second degree ofauthentication to verify that the end user belongs to a specificorganization or other entity (e.g., is a student on the universitycampus).

FIG. 4 is a schematic diagram illustrating a structure of a message 400,according to some embodiments, generated by a messaging clientapplication 104 for communication to a further messaging clientapplication 104 or the messaging server application 114. The content ofa particular message 400 is used to populate the message table 314stored within the database 120, accessible by the messaging serverapplication 114. Similarly, the content of a message 400 is stored inmemory as “in-transit” or “in-flight” data of the client device 102 orthe application server 112. The message 400 is shown to include thefollowing components:

-   -   A message identifier 402: a unique identifier that identifies        the message 400.    -   A message text payload 404: text to be generated by a user via a        user interface of the client device 102 and that is included in        the message 400.    -   A message image payload 406: image data captured by a camera        component of a client device 102 or retrieved from memory of a        client device 102 and included in the message 400.    -   A message video payload 408: video data captured by a camera        component or retrieved from a memory component of the client        device 102 and included in the message 400.    -   A message audio payload 410: audio data captured by a microphone        or retrieved from the memory component of the client device 102        and included in the message 400.    -   Message annotations 412: annotation data (e.g., filters,        stickers, or other enhancements) that represents annotations to        be applied to the message image payload 406, message video        payload 408, or message audio payload 410 of the message 400.    -   A message duration parameter 414: a parameter value indicating,        in seconds, the amount of time for which content of the message        400 (e.g., the message image payload 406, message video payload        408, and message audio payload 410) is to be presented or made        accessible to a user via the messaging client application 104.    -   A message geolocation parameter 416: geolocation data (e.g.,        latitudinal and longitudinal coordinates) associated with the        content payload of the message 400. Multiple message geolocation        parameter 416 values may be included in the payload, with each        of these parameter values being associated with respective        content items included in the content (e.g., a specific image in        the message image payload 406, or a specific video in the        message video payload 408).    -   A message story identifier 418: identifier values identifying        one or more content collections (e.g., “stories”) with which a        particular content item in the message image payload 406 of the        message 400 is associated. For example, multiple images within        the message image payload 406 may each be associated with        multiple content collections using identifier values.    -   A message tag 420: one or more tags, each of which is indicative        of the subject matter of content included in the message        payload. For example, where a particular image included in the        message image payload 406 depicts an animal (e.g., a lion), a        tag value may be included within the message tag 420 that is        indicative of the relevant animal. Tag values may be generated        manually, based on user input, or may be automatically generated        using, for example, image recognition.    -   A message sender identifier 422: an identifier (e.g., a        messaging system identifier, email address, or device        identifier) indicative of a user of the client device 102 on        which the message 400 was generated and from which the message        400 was sent.    -   A message receiver identifier 424: an identifier (e.g., a        messaging system identifier, email address, or device        identifier) indicative of a user of the client device 102 to        which the message 400 is addressed.

The contents (e.g., values) of the various components of the message 400may be pointers to locations in tables within which content data valuesare stored. For example, an image value in the message image payload 406may be a pointer to (or address of) a location within the image table308. Similarly, values within the message video payload 408 may point todata stored within the video table 310, values stored within the messageannotations 412 may point to data stored in the annotation table 312,values stored within the message story identifier 418 may point to datastored in the story table 306, and values stored within the messagesender identifier 422 and the message receiver identifier 424 may pointto user records stored within the entity table 302.

FIG. 5 is a schematic diagram illustrating an access-limiting process500, in terms of which access to content (e.g., an ephemeral message502, and associated multimedia payload of data) or a content collection(e.g., an ephemeral message story 504), may be time-limited (e.g., madeephemeral).

An ephemeral message 502 is shown to be associated with a messageduration parameter 506, the value of which determines an amount of timethat the ephemeral message 502 will be displayed to a receiving user ofthe ephemeral message 502 by the messaging client application 104. Inone embodiment, where the messaging client application 104 is a SNAPCHATapplication client, an ephemeral message 502 is viewable by a receivinguser for up to a maximum of 10 seconds, depending on the amount of timethat the sending user specifies using the message duration parameter506.

The message duration parameter 506 and the message receiver identifier424 are shown to be inputs to a message timer 512, which is responsiblefor determining the amount of time that the ephemeral message 502 isshown to a particular receiving user identified by the message receiveridentifier 424. In particular, the ephemeral message 502 will only beshown to the relevant receiving user for a time period determined by thevalue of the message duration parameter 506. The message timer 512 isshown to provide output to a more generalized ephemeral timer system202, which is responsible for the overall timing of display of content(e.g., an ephemeral message 502) to a receiving user.

The ephemeral message 502 is shown in FIG. 5 to be included within anephemeral message story 504 (e.g., a personal SNAPCHAT Story, or anevent story). The ephemeral message story 504 has an associated storyduration parameter 508, a value of which determines a time duration forwhich the ephemeral message story 504 is presented and accessible tousers of the messaging system 100. The story duration parameter 508, forexample, may be the duration of a music concert, where the ephemeralmessage story 504 is a collection of content pertaining to that concert.Alternatively, a user (either the owning user or a curator user) mayspecify the value for the story duration parameter 508 when performingthe setup and creation of the ephemeral message story 504.

Additionally, each ephemeral message 502 within the ephemeral messagestory 504 has an associated story participation parameter 510, a valueof which determines the duration of time for which the ephemeral message502 will be accessible within the context of the ephemeral message story504. Accordingly, a particular ephemeral message 502 may “expire” andbecome inaccessible within the context of the ephemeral message story504, prior to the ephemeral message story 504 itself expiring in termsof the story duration parameter 508. The story duration parameter 508,story participation parameter 510, and message receiver identifier 424each provide input to a story timer 514, which operationally determineswhether a particular ephemeral message 502 of the ephemeral messagestory 504 will be displayed to a particular receiving user and, if so,for how long. Note that the ephemeral message story 504 is also aware ofthe identity of the particular receiving user as a result of the messagereceiver identifier 424.

Accordingly, the story timer 514 operationally controls the overalllifespan of an associated ephemeral message story 504, as well as anindividual ephemeral message 502 included in the ephemeral message story504. In one embodiment, each and every ephemeral message 502 within theephemeral message story 504 remains viewable and accessible for a timeperiod specified by the story duration parameter 508. In a furtherembodiment, a certain ephemeral message 502 may expire, within thecontext of the ephemeral message story 504, based on a storyparticipation parameter 510. Note that a message duration parameter 506may still determine the duration of time for which a particularephemeral message 502 is displayed to a receiving user, even within thecontext of the ephemeral message story 504. Accordingly, the messageduration parameter 506 determines the duration of time that a particularephemeral message 502 is displayed to a receiving user, regardless ofwhether the receiving user is viewing that ephemeral message 502 insideor outside the context of an ephemeral message story 504.

The ephemeral timer system 202 may furthermore operationally remove aparticular ephemeral message 502 from the ephemeral message story 504based on a determination that it has exceeded an associated storyparticipation parameter 510. For example, when a sending user hasestablished a story participation parameter 510 of 24 hours fromposting, the ephemeral timer system 202 will remove the relevantephemeral message 502 from the ephemeral message story 504 after thespecified 24 hours. The ephemeral timer system 202 also operates toremove an ephemeral message story 504 either when the storyparticipation parameter 510 for each and every ephemeral message 502within the ephemeral message story 504 has expired, or when theephemeral message story 504 itself has expired in terms of the storyduration parameter 508.

In certain use cases, a creator of a particular ephemeral message story504 may specify an indefinite story duration parameter 508. In thiscase, the expiration of the story participation parameter 510 for thelast remaining ephemeral message 502 within the ephemeral message story504 will determine when the ephemeral message story 504 itself expires.In this case, a new ephemeral message 502, added to the ephemeralmessage story 504, with a new story participation parameter 510,effectively extends the life of an ephemeral message story 504 to equalthe value of the story participation parameter 510.

In response to the ephemeral timer system 202 determining that anephemeral message story 504 has expired (e.g., is no longer accessible),the ephemeral timer system 202 communicates with the messaging system100 (e.g., specifically, the messaging client application 104) to causean indicium (e.g., an icon) associated with the relevant ephemeralmessage story 504 to no longer be displayed within a user interface ofthe messaging client application 104. Similarly, when the ephemeraltimer system 202 determines that the message duration parameter 506 fora particular ephemeral message 502 has expired, the ephemeral timersystem 202 causes the messaging client application 104 to no longerdisplay an indicium (e.g., an icon or textual identification) associatedwith the ephemeral message 502.

FIG. 6 shows internal functional components of a coded vision system250, according to some example embodiments. The components themselvesare communicatively coupled (e.g., via appropriate interfaces) to eachother and to various data sources, so as to allow information to bepassed between the applications or so as to allow the applications toshare and access common data. Furthermore, the components access thedatabase 120 via the database server 118. As illustrated, the codedvision system 250 comprises a user interface engine 610, a detectionengine 620, a network interface engine 630, an action engine 640, andthe tracking engine 650. The user interface engine 610 managesgenerating user interface elements for display on the client device.Further, the user interface engine 610 manages receiving user interfaceactions through an input/output (I/O) device of the client device, suchas a touch screen. The detection engine 620 manages scanning the livefeed images and detecting different shapes or codes depicted in the livefeed. The network interface engine 630 is configured to send requestsfor content to a server, such as coded vision system 250, according tosome example embodiments. The action engine 640 is configured togenerate augmented reality elements using user data from an account thatis identified using the image feature. In some example embodiments, theaction engine 640 is located on a server (e.g., in coded vision system250), as discussed with reference to FIG. 11 below. The tracking engine650 manages tracking the image feature in the live feed and anchoringthe augmented reality elements with respect to the image feature.

FIG. 7 shows a flow diagram for a method 700 of implementing augmentedreality using coded user data, according to some example embodiments. Atoperation 705, the detection engine 620 identifies an image feature in alive feed. At operation 710, the network interface engine 630 accessesuser data associated with the detected image feature. At operation 715,action engine 640 generates overlay content with the user data. In someembodiments, at operation 715, the action engine 640 receives theoverlay content from a server configured to generate the overlaycontent, as discussed in further detail below. At operation 720, theaction engine 640 anchors the overlay content to the image feature inthe live feed.

FIGS. 8A and 8B show an example of a client device performing the method700 of FIG. 7, according to some example embodiments. In particular,FIG. 8A shows a client device 800 displaying a user interface 805 forimplementing augmented reality using coded user data. The user interface805 is generated by the user interface engine 610 from a clientapplication (e.g., coded vision system 250) executing on the clientdevice 800, according to some embodiments. As illustrated, the userinterface 805 is displaying one or more frames (e.g., live video) from acamera on the backside (not depicted) of client device 800. In the oneor more frames, an image feature 810 is depicted. In some exampleembodiments, the image feature is coded with dots, lines, or other typesof coding that the detection engine can use to identify a userassociated with the image feature 810. Further details of an exampleapproaches using image features are described in: application Ser. No.15/262,942, titled “PRESENTING AN AUGMENTED REALITY WITHIN A CUSTOMGRAPHIC”, filed on Sep. 12, 2016; U.S. Pat. No. 9,111,164, titled“CUSTOM FUNCTIONAL PATTERNS FOR OPTICAL BARCODES”, filed on Jan. 19,2015; application Ser. No. 14/595,712, titled “GUIDED PERSONAL IDENTITYBASED ACTIONS”, filed on Jan. 13, 2015; and application Ser. No.15/074,629, titled “FACIAL PATTERNS FOR OPTICAL BARCODES”, filed on Jan.19, 2015; which are hereby incorporated by reference in entirety.

FIG. 8B shows the client device 800 with the user interface 805displaying augmented reality elements, according to some exampleembodiments. After the image feature is scanned and the coding is usedto identify a corresponding user and user profile on the applicationserver 112, the coded vision system 250 uses user data stored in theuser profile (e.g., stored in database 120) to generate overlay contentfor the live feed. In the example shown, image post data (e.g., imagesfrom ephemeral messages 502 published by the user over social media) areused to populate one or more bubbles 815. The one or more bubbles 815are part of an animation sequence that depicts the bubbles as emanatingfrom the image feature 810, according to some example embodiments.

Further, upon the image feature being scanned and the user profile beingidentified, a add button 820 can be shown with the overlay content. Theadd button 820 allows the user operating client device 800 (notdepicted) to add the user whose image feature was scanned as a friend onthe social graph. After the users are friends, they may then exchangeephemeral messages 502 using their respective message clientapplications (e.g., message client app 504).

FIG. 9 shows a flow diagram for a method 900 for implementing augmentedreality using user data and a coded image feature, according to someexample embodiments. At operation 905, the detection engine 620identifies an image feature in a live feed. At operation 907, thedetection engine 620 determines that the image feature is associatedwith a user profile of a first user. At operation 910, the networkinterface engine 630 accesses the first user's user data on a server,e.g., application server 112. At operation 915, the network interfaceengine 630 accesses a second user's user data on the server. The seconduser is the user that is operating the coded vision system throughanother the client device. At operation 920, the action engine 640generates a combined depiction that shows the user data of the firstuser interacting with user data of the second user. At operation 925,the action engine 640 overlays the combined depiction over the livefeed. At operation 930, the action engine 640 anchors the combineddepiction to the image feature in the live feed. For example, thecombined depiction is anchored to the image feature such that when theclient device is moved to view the image feature from different angles,the combined depiction keeps its position with respect to the imagefeature in the live feed. FIGS. 10B and 10C, discussed below, furthershow an example of anchoring a combined depiction as the client device(a smartphone) is rotated around the image feature.

FIGS. 10A-C show an example client device 1000 implementing augmentedreality using user data and coded image features, according to someexample embodiments. In particular, as illustrated in the example ofFIG. 10A, the client device 1000 includes a user interface 1005 that ismanaged by the user interface engine 610. As illustrated, the userinterface 1005 is displaying a live feed of image data from an imagesensor located on the backside (not depicted) of the client device 1000.The live feed comprises one or more image frames played sequentially(e.g., a live video feed). In the live feed, an image feature 1010 isdepicted. The image feature 1010 is an image that the detection featureis pre-configured to recognize. Further, according to some exampleembodiments, the image feature 1010 has one or more dots or bars thatcorrespond to a code language (e.g., a barcode) that identifies a useraccount of a user. The detection engine 620 is configured to identifythe image feature 1010 and use the code (e.g., dot configuration) toidentify a user account of a user. In this way, the image feature 1010functions as an account identifier for a user.

FIG. 10B shows an example of the client device 1000 displaying acombined depiction of user data from two different users, according tosome example embodiments. As illustrated, in response to the imagefeature 1010 being scanned and the user account of a user beingidentified, a combined depiction 1015 (e.g., combined avatar) isgenerated that depicts first user data 1020 of a first user interactingwith second user data 1025 of a second user. In some exampleembodiments, the first user data 1020 is an avatar created by the firstuser (e.g., user whose user profile is identified by the code in imagefeature 1010) and the second user data 1025 is another avatar created bythe second user (e.g., user of the client device 1000). The combineddepiction 1015 is generated using a combined avatar template thatspecifies how each avatar should be arranged or configured so that theavatars appear to be interacting with each other.

FIG. 10C shows an example of the client device 1000 displaying acombined depiction of user data from two different users from adifferent perspective, according to some example embodiments. Tomaintain the appearance that the image feature 1010 is the source of theaugmented reality elements (e.g., one or more bubbles 815 in FIG. 8B orthe combined depiction 1015), tracking is implemented. In particular,for example, a tracking engine 650 is implemented to anchor theaugmented reality elements to the image feature. In this way, withreference to FIG. 8B, the one or more bubbles 815 can be played as ananimation that makes the image feature 810 appear as the source of thebubbles. Similarly, with reference to FIG. 10C, the combined depiction1015 may be animated so the first avatar (e.g., user data 1020) and thecartoon present appear to pop out of the image feature 1010. Further, asillustrated in FIG. 10C, as the user (not depicted) moves the clientdevice 1000, thereby causing the image feature 1010 to move in the livefeed, the tracking engine 650 tracks the image feature location andanchors the augmented reality elements to the image feature location ata fixed position. Further, as the user rotates the client device 1000around the image feature 1010, the tracking engine 650 can rotate thecombined depiction 1015 to face the user. Further, rotation of theclient device 1000 may cause the depicted augmented elements (e.g.,combined depiction) to rotate in three-dimensions, animate (e.g.,cartoon confetti may be depicted as falling across the user interface1005), and so forth. In some embodiments, the augmented elements arethree-dimensional models that can animate or be modified (e.g., rotatedabout the image feature 1010) in response to manipulation (e.g.,movement) of the client device 1000.

FIG. 11 shows a method 1100 for implementing augmented reality usinguser data and coded image features, according to some exampleembodiments. In FIG. 11, operations performed on the application serverare executed using an example of a coded vision system 250, which inFIG. 11 is labeled as a app engine 1111. The operations external to theapp engine 1111 are executed on the coded vision system 250 on clientdevice 102. At operation 1105, the coded vision system 250 detects animage feature through its image sensor. In some example embodiments, theimage feature is imaged in the live feed. To trigger the detectionengine 620 to scan and identify the image feature, the user performs auser action (e.g., screen tap) on the code in the live feed, accordingto some example embodiments. At operation 1110, the detection engine 620runs a code checker that checks whether the code in the image feature isvalid. In some example embodiments, all codes are generated using anequation or algorithm. In those embodiments, the detection engine 620can use the equation or algorithm to check whether the code is valid. Ifthe code is not valid, the user interface engine 610 generates an errormessage (e.g. “Scanned code not valid.”) for display on the displayscreen of the client device.

If the code is valid, at operation 1115, the user interface engine 610generates a “Loading” message for display on the client device. Further,the code from the image feature or the image feature image data istransmitted to the app engine 1111 for further processing. At operation1120, the app engine 1111 receives the code or the image feature imagedata and uses it to locate a user profile of a user. The image featureis thus an identifier for the user profile account. At operation 1125,data is transmitted to the client device 102. In some embodiments, thedata includes an user account identifier (e.g., “snapcode identifier”),a uniform resource locator (URL) for a content package, and a bitmojiID, where a Bitmoji® is a name for a type of reconfigurable avatardesigned by the user. Bitmoji's are accessible as part of a networkplatform connectable to over a network as a service. The content packagemay include content 1135 such as lens metadata (e.g., video filterdata), that can configure the live feed to display a video effect (e.g.,blur, swirl, augmented reality clouds animated to appear raining). Insome embodiments, the content 1135 is accessible to the user only if theuser scans a given image feature. In those embodiments, some imagefeatures may be owned/managed by a company. The company may configure avideo effect to show their logo, brand name, or promotional item. Uponscanning the image feature, the company's content package may beunlocked in that that the content package URL is sent to the userdevice. Further, according to some example embodiments, the contentincludes a combined depiction template identifier.

At operation 1130, the coded vision system 250 requests the content 1135by directing a request to the URL. In response, the app engine 1111sends the content 1135 to the client device 102, and the client device102 prepares to render the content at operation 1140. At operation 1145,if the content does not require a combined depiction (e.g., a“friendmoji” that shows two avatars interacting with each other), thecoded vision system 250 displays the content (e.g. applies a videoeffect to the live feed) at operation 1150. On the other hand, if, atoperation 1145, the content does require a combined depiction, then atoperation 1155, the coded vision system 250 sends a request to a servertarget (e.g., an action engine 760 executed on app engine 1111 having anaddress “/bitmoji/image”), requesting the combined depiction content. Insome embodiments, the request of operation 1155 includes an identifieridentifying the first user account, the second user account, and thetype of combined depiction content to be used. In some exampleembodiments, the contented displayed at operation 1150 includes one ormore of: a combined avatar of the two users (e.g., a scanning user and auser whose scannable image was scanned), overlay content using imagesfrom ephemeral messages 502, or an add button (e.g., add button 820,FIG. 8B).

In some example embodiments, the client device stores a complete list ofcombined depiction templates and IDs, and an action engine 1160 on theapp engine 1111 manages generating the combined depictions. Once theaction engine 1160 generates the combined depiction 1165, it sends thecombined depiction 1165 to the client device 102. The client devicereceives the combined depiction 1165 and anchors the combined depiction1165 to the image feature in the live feed, as discussed above. In someexample embodiments, if at operation 1145 the content requires acombined depiction, but the user associated with the image feature doesnot have an avatar (e.g., a Bitmoji®) configured, the action engineprepares fall back content. For example, instead of an avatar poppingout of a present (as depicted in combined depiction 1165) the presentcan be animated as exploding with confetti.

FIG. 12 is a block diagram illustrating an example software architecture1206, which may be used in conjunction with various hardwarearchitectures herein described. FIG. 12 is a non-limiting example of asoftware architecture, and it will be appreciated that many otherarchitectures may be implemented to facilitate the functionalitydescribed herein. The software architecture 1206 may execute on hardwaresuch as a machine 1200 of FIG. 12 that includes, among other things,processors, memory, and I/O components. A representative hardware layer1252 is illustrated and can represent, for example, the machine 1200 ofFIG. 12. The representative hardware layer 1252 includes a processingunit 1254 having associated executable instructions 1204. The executableinstructions 1204 represent the executable instructions of the softwarearchitecture 1206, including implementation of the methods, components,and so forth described herein. The hardware layer 1252 also includes amemory/storage 1256, which also has the executable instructions 1204.The hardware layer 1252 may also comprise other hardware 1258.

In the example architecture of FIG. 12, the software architecture 1206may be conceptualized as a stack of layers where each layer providesparticular functionality. For example, the software architecture 1206may include layers such as an operating system 1202, libraries 1220,frameworks/middleware 1218, applications 1216, and a presentation layer1214. Operationally, the applications 1216 and/or other componentswithin the layers may invoke API calls 1208 through the software stackand receive a response in the form of messages 1212. The layersillustrated are representative in nature and not all softwarearchitectures have all layers. For example, some mobile orspecial-purpose operating systems may not provide aframeworks/middleware 1218, while others may provide such a layer. Othersoftware architectures may include additional or different layers.

The operating system 1202 may manage hardware resources and providecommon services. The operating system 1202 may include, for example, akernel 1222, services 1224, and drivers 1226. The kernel 1222 may act asan abstraction layer between the hardware and the other software layers.For example, the kernel 1222 may be responsible for memory management,processor management (e.g., scheduling), component management,networking, security settings, and so on. The services 1224 may provideother common services for the other software layers. The drivers 1226are responsible for controlling or interfacing with the underlyinghardware. For instance, the drivers 1226 include display drivers, cameradrivers, Bluetooth® drivers, flash memory drivers, serial communicationdrivers (e.g., Universal Serial Bus (USB) drivers), Wi-Fi® drivers,audio drivers, power management drivers, and so forth depending on thehardware configuration.

The libraries 1220 provide a common infrastructure that is used by theapplications 1216 and/or other components and/or layers. The libraries1220 provide functionality that allows other software components toperform tasks in an easier fashion than by interfacing directly with theunderlying operating system 1202 functionality (e.g., kernel 1222,services 1224, and/or drivers 1226). The libraries 1220 may includesystem libraries 1244 (e.g., C standard library) that may providefunctions such as memory allocation functions, string manipulationfunctions, mathematical functions, and the like. In addition, thelibraries 1220 may include API libraries 1246 such as media libraries(e.g., libraries to support presentation and manipulation of variousmedia formats such as MPEG4, H.264, MP3, AAC, AMR, JPG, or PNG),graphics libraries (e.g., an OpenGL framework that may be used to rendertwo dimensional (2D) and three dimensional (3D) graphic content on adisplay), database libraries (e.g., SQLite that may provide variousrelational database functions), web libraries (e.g., WebKit that mayprovide web browsing functionality), and the like. The libraries 1220may also include a wide variety of other libraries 1248 to provide manyother APIs to the applications 1216 and other softwarecomponents/modules.

The frameworks/middleware 1218 provide a higher-level commoninfrastructure that may be used by the applications 1216 and/or othersoftware components/modules. For example, the frameworks/middleware 1218may provide various graphic user interface (GUI) functions, high-levelresource management, high-level location services, and so forth. Theframeworks/middleware 1218 may provide a broad spectrum of other APIsthat may be utilized by the applications 1216 and/or other softwarecomponents/modules, some of which may be specific to a particularoperating system 1202 or platform.

The applications 1216 include built-in applications 1238 and/orthird-party applications 1240. Examples of representative built-inapplications 1238 may include, but are not limited to, a contactsapplication, a browser application, a book reader application, alocation application, a media application, a messaging application,and/or a game application. The third-party applications 1240 may includean application developed using the ANDROID™ or IOS™ software developmentkit (SDK) by an entity other than the vendor of the particular platform,and may be mobile software running on a mobile operating system such asIOS™, ANDROID™, WINDOWS® Phone, or other mobile operating systems. Thethird-party applications 1240 may invoke the API calls 1208 provided bythe mobile operating system (such as the operating system 1202) tofacilitate functionality described herein.

The applications 1216 may use built-in operating system functions (e.g.,kernel 1222, services 1224, and/or drivers 1226), libraries 1220, andframeworks/middleware 1218 to create user interfaces to interact withusers of the system. Alternatively, or additionally, in some systems,interactions with a user may occur through a presentation layer, such asthe presentation layer 1214. In these systems, the application/component“logic” can be separated from the aspects of the application/componentthat interact with a user.

FIG. 13 is a block diagram illustrating components of a machine 1300,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically, FIG. 13 shows a diagrammatic representation of the machine1300 in the example form of a computer system, within which instructions1316 (e.g., software, a program, an application, an applet, an app, orother executable code) for causing the machine 1300 to perform any oneor more of the methodologies discussed herein may be executed. As such,the instructions 1316 may be used to implement modules or componentsdescribed herein. The instructions 1316 transform the general,non-programmed machine 1300 into a particular machine 1300 programmed tocarry out the described and illustrated functions in the mannerdescribed. In alternative embodiments, the machine 1300 operates as astandalone device or may be coupled (e.g., networked) to other machines.In a networked deployment, the machine 1300 may operate in the capacityof a server machine or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine 1300 may comprise, but not be limitedto, a server computer, a client computer, a personal computer (PC), atablet computer, a laptop computer, a netbook, a set-top box (STB), apersonal digital assistant (PDA), an entertainment media system, acellular telephone, a smartphone, a mobile device, a wearable device(e.g., a smart watch), a smart home device (e.g., a smart appliance),other smart devices, a web appliance, a network router, a networkswitch, a network bridge, or any machine capable of executing theinstructions 1316, sequentially or otherwise, that specify actions to betaken by the machine 1300. Further, while only a single machine 1300 isillustrated, the term “machine” shall also be taken to include acollection of machines that individually or jointly execute theinstructions 1316 to perform any one or more of the methodologiesdiscussed herein.

The machine 1300 may include processors 1310, memory/storage 1330, andI/O components 1350, which may be configured to communicate with eachother such as via a bus 1302. The memory/storage 1330 may include amemory 1332, such as a main memory, or other memory storage, and astorage unit 1336, both accessible to the processors 1310 such as viathe bus 1302. The storage unit 1336 and memory 1332 store theinstructions 1316 embodying any one or more of the methodologies orfunctions described herein. The instructions 1316 may also reside,completely or partially, within the memory 1332, within the storage unit1336, within at least one of the processors 1310 (e.g., within theprocessor's cache memory), or any suitable combination thereof, duringexecution thereof by the machine 1300. Accordingly, the memory 1332, thestorage unit 1336, and the memory of the processors 1310 are examples ofmachine-readable media.

The I/O components 1350 may include a wide variety of components toreceive input, provide output, produce output, transmit information,exchange information, capture measurements, and so on. The specific I/Ocomponents 1350 that are included in a particular machine 1300 willdepend on the type of machine. For example, portable machines such asmobile phones will likely include a touch input device or other suchinput mechanisms, while a headless server machine will likely notinclude such a touch input device. It will be appreciated that the I/Ocomponents 1350 may include many other components that are not shown inFIG. 13. The I/O components 1350 are grouped according to functionalitymerely for simplifying the following discussion and the grouping is inno way limiting. In various example embodiments, the I/O components 1350may include output components 1352 and input components 1354. The outputcomponents 1352 may include visual components (e.g., a display such as aplasma display panel (PDP), a light-emitting diode (LED) display, aliquid-crystal display (LCD), a projector, or a cathode ray tube (CRT)),acoustic components (e.g., speakers), haptic components (e.g., avibratory motor, resistance mechanisms), other signal generators, and soforth. The input components 1354 may include alphanumeric inputcomponents (e.g., a keyboard, a touch screen configured to receivealphanumeric input, a photo-optical keyboard, or other alphanumericinput components), point-based input components (e.g., a mouse, atouchpad, a trackball, a joystick, a motion sensor, or other pointinginstruments), tactile input components (e.g., a physical button, a touchscreen that provides location and/or force of touches or touch gestures,or other tactile input components), audio input components (e.g., amicrophone), and the like.

In further example embodiments, the I/O components 1350 may includebiometric components 1356, motion components 1358, environmentcomponents 1360, or position components 1362 among a wide array of othercomponents. For example, the biometric components 1356 may includecomponents to detect expressions (e.g., hand expressions, facialexpressions, vocal expressions, body gestures, or eye tracking), measurebiosignals (e.g., blood pressure, heart rate, body temperature,perspiration, or brain waves), identify a person (e.g., voiceidentification, retinal identification, facial identification,fingerprint identification, or electroencephalogram-basedidentification), and the like. The motion components 1358 may includeacceleration sensor components (e.g., accelerometer), gravitation sensorcomponents, rotation sensor components (e.g., gyroscope), and so forth.The environment components 1360 may include, for example, illuminationsensor components (e.g., photometer), temperature sensor components(e.g., one or more thermometers that detect ambient temperature),humidity sensor components, pressure sensor components (e.g.,barometer), acoustic sensor components (e.g., one or more microphonesthat detect background noise), proximity sensor components (e.g.,infrared sensors that detect nearby objects), gas sensors (e.g., gassensors to detect concentrations of hazardous gases for safety or tomeasure pollutants in the atmosphere), or other components that mayprovide indications, measurements, or signals corresponding to asurrounding physical environment. The position components 1362 mayinclude location sensor components (e.g., a GPS receiver component),altitude sensor components (e.g., altimeters or barometers that detectair pressure from which altitude may be derived), orientation sensorcomponents (e.g., magnetometers), and the like.

Communication may be implemented using a wide variety of technologies.The I/O components 1350 may include communication components 1364operable to couple the machine 1300 to a network 1380 or devices 1370via a coupling 1382 and a coupling 1372, respectively. For example, thecommunication components 1364 may include a network interface componentor other suitable device to interface with the network 1380. In furtherexamples, the communication components 1364 may include wiredcommunication components, wireless communication components, cellularcommunication components, Near Field Communication (NFC) components,Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components,and other communication components to provide communication via othermodalities. The devices 1370 may be another machine or any of a widevariety of peripheral devices (e.g., a peripheral device coupled via aUSB).

Moreover, the communication components 1364 may detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 1364 may include Radio Frequency Identification(RFID) tag reader components, NFC smart tag detection components,optical reader components (e.g., an optical sensor to detectone-dimensional barcodes such as Universal Product Code (UPC) barcode,multi-dimensional barcodes such as Quick Response (QR) code, Aztec code,Data Matrix, Dataglyph, MaxiCode, PDF413, Ultra Code, UCC RSS-2Dbarcode, and other optical codes), or acoustic detection components(e.g., microphones to identify tagged audio signals). In addition, avariety of information may be derived via the communication components1364, such as location via Internet Protocol (IP) geolocation, locationvia Wi-Fi® signal triangulation, location via detecting an NFC beaconsignal that may indicate a particular location, and so forth.

GLOSSARY

“CARRIER SIGNAL” in this context refers to any intangible medium that iscapable of storing, encoding, or carrying instructions for execution bythe machine, and includes digital or analog communications signals orother intangible media to facilitate communication of such instructions.Instructions may be transmitted or received over the network using atransmission medium via a network interface device and using any one ofa number of well-known transfer protocols.

“CLIENT DEVICE” in this context refers to any machine that interfaces toa communications network to obtain resources from one or more serversystems or other client devices. A client device may be, but is notlimited to, a mobile phone, desktop computer, laptop, PDA, smartphone,tablet, ultrabook, netbook, multi-processor system, microprocessor-basedor programmable consumer electronics system, game console, set-top box,or any other communication device that a user may use to access anetwork.

“COMMUNICATIONS NETWORK” in this context refers to one or more portionsof a network that may be an ad hoc network, an intranet, an extranet, avirtual private network (VPN), a local area network (LAN), a wirelessLAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), ametropolitan area network (MAN), the Internet, a portion of theInternet, a portion of the Public Switched Telephone Network (PSTN), aplain old telephone service (POTS) network, a cellular telephonenetwork, a wireless network, a Wi-Fi® network, another type of network,or a combination of two or more such networks. For example, a network ora portion of a network may include a wireless or cellular network andthe coupling may be a Code Division Multiple Access (CDMA) connection, aGlobal System for Mobile communications (GSM) connection, or anothertype of cellular or wireless coupling. In this example, the coupling mayimplement any of a variety of types of data transfer technology, such asSingle Carrier Radio Transmission Technology (1×RTT), Evolution-DataOptimized (EVDO) technology, General Packet Radio Service (GPRS)technology, Enhanced Data rates for GSM Evolution (EDGE) technology,third Generation Partnership Project (3GPP) including 3G, fourthgeneration wireless (4G) networks, Universal Mobile TelecommunicationsSystem (UMTS), High-Speed Packet Access (HSPA), WorldwideInteroperability for Microwave Access (WiMAX), Long-Term Evolution (LTE)standard, others defined by various standard-setting organizations,other long-range protocols, or other data transfer technology.

“EMPHEMERAL MESSAGE” in this context refers to a message that isaccessible for a time-limited duration. An ephemeral message may be atext, an image, a video, and the like. The access time for the ephemeralmessage may be set by the message sender. Alternatively, the access timemay be a default setting or a setting specified by the recipient.Regardless of the setting technique, the message is transitory.

“MACHINE-READABLE MEDIUM” in this context refers to a component, adevice, or other tangible media able to store instructions and datatemporarily or permanently and may include, but is not limited to,random-access memory (RAM), read-only memory (ROM), buffer memory, flashmemory, optical media, magnetic media, cache memory, other types ofstorage (e.g., Erasable Programmable Read-Only Memory (EPROM)), and/orany suitable combination thereof. The term “machine-readable medium”should be taken to include a single medium or multiple media (e.g., acentralized or distributed database, or associated caches and servers)able to store instructions. The term “machine-readable medium” shallalso be taken to include any medium, or combination of multiple media,that is capable of storing instructions (e.g., code) for execution by amachine, such that the instructions, when executed by one or moreprocessors of the machine, cause the machine to perform any one or moreof the methodologies described herein. Accordingly, a “machine-readablemedium” refers to a single storage apparatus or device, as well as“cloud-based” storage systems or storage networks that include multiplestorage apparatus or devices. The term “machine-readable medium”excludes signals per se.

“COMPONENT” in this context refers to a device, a physical entity, orlogic having boundaries defined by function or subroutine calls, branchpoints, APIs, or other technologies that provide for the partitioning ormodularization of particular processing or control functions. Componentsmay be combined via their interfaces with other components to carry outa machine process. A component may be a packaged functional hardwareunit designed for use with other components and a part of a program thatusually performs a particular function of related functions. Componentsmay constitute either software components (e.g., code embodied on amachine-readable medium) or hardware components. A “hardware component”is a tangible unit capable of performing certain operations and may beconfigured or arranged in a certain physical manner. In various exampleembodiments, one or more computer systems (e.g., a standalone computersystem, a client computer system, or a server computer system) or one ormore hardware components of a computer system (e.g., a processor or agroup of processors) may be configured by software (e.g., an applicationor application portion) as a hardware component that operates to performcertain operations as described herein. A hardware component may also beimplemented mechanically, electronically, or any suitable combinationthereof. For example, a hardware component may include dedicatedcircuitry or logic that is permanently configured to perform certainoperations. A hardware component may be a special-purpose processor,such as a Field-Programmable Gate Array (FPGA) or anApplication-Specific Integrated Circuit (ASIC). A hardware component mayalso include programmable logic or circuitry that is temporarilyconfigured by software to perform certain operations. For example, ahardware component may include software executed by a general-purposeprocessor or other programmable processor. Once configured by suchsoftware, hardware components become specific machines (or specificcomponents of a machine) uniquely tailored to perform the configuredfunctions and are no longer general-purpose processors. It will beappreciated that the decision to implement a hardware componentmechanically, in dedicated and permanently configured circuitry, or intemporarily configured circuitry (e.g., configured by software) may bedriven by cost and time considerations. Accordingly, the phrase“hardware component” (or “hardware-implemented component”) should beunderstood to encompass a tangible entity, be that an entity that isphysically constructed, permanently configured (e.g., hardwired), ortemporarily configured (e.g., programmed) to operate in a certain manneror to perform certain operations described herein.

Considering embodiments in which hardware components are temporarilyconfigured (e.g., programmed), each of the hardware components need notbe configured or instantiated at any one instance in time. For example,where a hardware component comprises a general-purpose processorconfigured by software to become a special-purpose processor, thegeneral-purpose processor may be configured as respectively differentspecial-purpose processors (e.g., comprising different hardwarecomponents) at different times. Software accordingly configures aparticular processor or processors, for example, to constitute aparticular hardware component at one instance of time and to constitutea different hardware component at a different instance of time.

Hardware components can provide information to, and receive informationfrom, other hardware components. Accordingly, the described hardwarecomponents may be regarded as being communicatively coupled. Wheremultiple hardware components exist contemporaneously, communications maybe achieved through signal transmission (e.g., over appropriate circuitsand buses) between or among two or more of the hardware components. Inembodiments in which multiple hardware components are configured orinstantiated at different times, communications between or among suchhardware components may be achieved, for example, through the storageand retrieval of information in memory structures to which the multiplehardware components have access. For example, one hardware component mayperform an operation and store the output of that operation in a memorydevice to which it is communicatively coupled. A further hardwarecomponent may then, at a later time, access the memory device toretrieve and process the stored output. Hardware components may alsoinitiate communications with input or output devices, and can operate ona resource (e.g., a collection of information).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implementedcomponents that operate to perform one or more operations or functionsdescribed herein. As used herein, “processor-implemented component”refers to a hardware component implemented using one or more processors.Similarly, the methods described herein may be at least partiallyprocessor-implemented, with a particular processor or processors beingan example of hardware. For example, at least some of the operations ofa method may be performed by one or more processors orprocessor-implemented components. Moreover, the one or more processorsmay also operate to support performance of the relevant operations in a“cloud computing” environment or as a “software as a service” (SaaS).For example, at least some of the operations may be performed by a groupof computers (as examples of machines including processors), with theseoperations being accessible via a network (e.g., the Internet) and viaone or more appropriate interfaces (e.g., an API). The performance ofcertain of the operations may be distributed among the processors, notonly residing within a single machine, but deployed across a number ofmachines. In some example embodiments, the processors orprocessor-implemented components may be located in a single geographiclocation (e.g., within a home environment, an office environment, or aserver farm). In other example embodiments, the processors orprocessor-implemented components may be distributed across a number ofgeographic locations.

“PROCESSOR” in this context refers to any circuit or virtual circuit (aphysical circuit emulated by logic executing on an actual processor)that manipulates data values according to control signals (e.g.,“commands,” “op codes,” “machine code,” etc.) and which producescorresponding output signals that are applied to operate a machine. Aprocessor may, for example, be a Central Processing Unit (CPU), aReduced Instruction Set Computing (RISC) processor, a ComplexInstruction Set Computing (CISC) processor, a Graphics Processing Unit(GPU), a Digital Signal Processor (DSP), an ASIC, a Radio-FrequencyIntegrated Circuit (RFIC), or any combination thereof. A processor mayfurther be a multi-core processor having two or more independentprocessors (sometimes referred to as “cores”) that may executeinstructions contemporaneously.

“TIMESTAMP” in this context refers to a sequence of characters orencoded information identifying when a certain event occurred (forexample, giving date and time of day, sometimes accurate to a smallfraction of a second).

What is claimed is:
 1. A method comprising: generating, on a firstclient device of a first user, an electronic message for transmission toa second client device of a second user, the first user having a firstuser account on a network platform and the second user having a seconduser account on the network platform; determining whether the seconduser account on the network platform has avatar data of the second user;in response to determining that the second user account has avatar dataof the second user, receiving, from a server of the network platform, aresponse comprising the avatar data of the second user; generating acombined avatar that displays the avatar data of the second user withavatar data of the first user, the combined avatar generated from acombined avatar template that arranges the avatar data of the first userand the avatar data of the second user into a specified configuration;displaying the combined avatar on a display device of the first clientdevice; and transmitting, to the second client device, the electronicmessage including the generated combined avatar.
 2. The method of claim1, wherein the combined avatar is an animation.
 3. The method of claim1, wherein the electronic message is an ephemeral message accessiblethrough the network platform.
 4. The method of claim 3, wherein theephemeral message automatically expires after a specified time durationsuch that the second client device cannot access the ephemeral messagethrough the network platform after expiration.
 5. The method of claim 1,further comprising: generating one or more images using an image sensorof the first client device; displaying the one or more images on thedisplay device of the first client device; and receiving a user actionon the one or more images, wherein determining whether the second useraccount has avatar data is in response to the user action on the one ormore images on the first client device.
 6. The method of claim 5,wherein the one or more images displays an image feature that is anidentifier of the second user account on the network platform, andwherein the user action is a selection of the identifier in the one ormore images.
 7. The method of claim 6, wherein determining whether thesecond user account on the network platform has avatar data of thesecond user comprises: generating a code from the image feature; andtransmitting the code to the server of the network platform.
 8. Themethod of claim 5, further comprising: displaying, on the displaydevice, the combined avatar on the one or more images.
 9. The method ofclaim 8, wherein the electronic message comprises a presentation of thecombined avatar overlaid on the one or more images.
 10. The method ofclaim 5, wherein the response comprises lens metadata configured tomodify the one or more images using one or more visual effects.
 11. Themethod of claim 10, further comprising: applying the one or more visualeffects to the one or more images using the lens metadata to generateone or more modified images; and displaying the one or more modifiedimages on the display device of the first client device.
 12. The methodof claim 11, wherein applying the one or more visual effects to the oneor more images comprises: detecting a display of a face of a user in theone or more images; and generating the one or more modified images bymodifying the display of the face using the lens metadata.
 13. A clientdevice comprising: one or more processors of a machine; and a displaydevice; a memory storing instructions that, when executed by the one ormore processors, cause the machine to perform operations comprising:generating, on the client device of a first user, an electronic messagefor transmission to another client device of a second user, the firstuser having a first user account on a network platform and the seconduser having a second user account on the network platform; determiningwhether the second user account on the network platform has avatar dataof the second user; in response to determining that the second useraccount has avatar data from the second user, receiving, from a serverof the network platform, a response comprising the avatar data of thesecond user; generating a combined avatar that displays the avatar dataof the second user with avatar data of the first user, the combinedavatar generated from a combined avatar template that arranges theavatar data of the first user and the avatar data of the second userinto a specified configuration; displaying the combined avatar on thedisplay device of the client device; and transmitting, to the anotherclient device, the electronic message with the generated combinedavatar.
 14. The client device of claim 13, wherein the combined avataris an animation.
 15. The client device of claim 13, wherein theelectronic message is an ephemeral message accessible through thenetwork platform.
 16. The client device of claim 15, wherein theephemeral message automatically expires after a specified time durationsuch that the another client device cannot access the ephemeral messagethrough the network platform after expiration.
 17. The client device ofclaim 13, the operations further comprising: generating one or moreimages using an image sensor of the client device; displaying the one ormore images on the display device of the client device; and receiving auser action on the one or more images, wherein determining whether thesecond user account has avatar data is in response to the user action onthe one or more images.
 18. A machine-readable storage device embodyinginstructions that, when executed by a client device, cause the clientdevice to perform operations comprising: generating, on the clientdevice of a first user, an electronic message for transmission toanother client device of a second user, the first user having a firstuser account on a network platform and the second user having a seconduser account on the network platform; determining whether the seconduser account on the network platform has avatar data of the second user;in response to determining that the second user account has avatar datafrom the second user, receiving, from a server of the network platform,a response comprising the avatar data of the second user; generating acombined avatar that displays the avatar data of the second user withavatar data of the first user, the combined avatar generated from acombined avatar template that arranges the avatar data of the first userand the avatar data of the second user into a specified configuration;displaying the combined avatar on a display device of the client device;and transmitting, to the another client device, the electronic messagewith the generated combined avatar.
 19. The machine-readable storagedevice of claim 18, wherein the combined avatar is an animation.
 20. Themachine-readable storage device of claim 18, the operations furthercomprising: generating one or more images using an image sensor of theclient device; displaying the one or more images on the display deviceof the client device; and receiving a user action on the one or moreimages, wherein determining whether the second user account has avatardata is in response to the user action on the one or more images on theclient device.